TMF620 Product Catalog Management API (Outbound)

The TMF620 application is built and configured with the Aria Connector.

If you want to configure the application with a different MuleSoft connector, or make any other changes in the application (for example, orchestration change, data transformation, or logic) follow the steps::

Download TMF 620 project file from Anypoint Runtime Manager

• Log in to the Mulesoft Anypoint Platform instance where the API was deployed.
• Navigate to Runtime Manager and locate the deployed API. NOTE: This API should be in the Running phase.
• Click on name of the API
• Under Application File, click the file name to download the project’s JAR file.
• After you download the JAR file to your local system, import it into Anypoint Studio to modify the project’s configuration or add and update data transformation.

Connect with Various Target Systems Using Anypoint Exchange connectors

After the project file is imported and scaffold in Anypoint studio, various application-based connectors can be added to the project as necessary.

1. From Anypoint Studio’s Mule Palette, click Search in Exchange.
2. Sign in to Anypoint Platform if you’re not already signed in.
3. After you are authenticated, search for the name of the connector and add the necessary connectors from the Available Compatible Modules section to the Selected Modules section.
4. Click Finish and verify that the newly-added connector appears in the Mule Palette.

Updating Mule Runtime Properties

Optionally, if you need to update the Mule runtime properties of the app in Anypoint Runtime Manager, follow the steps below:

1. In Anypoint Platform, navigate to Runtime Manager and click the name of API to update properties
2. Click on Settings and select Properties tab
3. Add or update the necessary properties here with Key: Value pair

Required Properties:

API Configuration:
- api_id = {API ID for API Manager autodiscovery}
- env = {Environment: dev, qa, stg, or prod}

Salesforce OAuth2 Client Credentials Configuration:
- secure::salesforce.consumer_key = {OAuth Consumer Key from Salesforce Connected App}
- secure::salesforce.consumer_secret = {OAuth Consumer Secret from Salesforce Connected App}
- salesforce.OAuth.tokenUrl = {Salesforce OAuth token URL, e.g., https://MyCompany.my.salesforce.com/services/oauth2/token}
- salesforce.namespace = {Salesforce namespace prefix}

VM Queue Configuration:
- vm.queueName = {Queue name, e.g., tmf620-product-catalog-queue}

External System Configuration (Aria):
- aria.hostname = {Aria instance hostname, e.g., http://aria-prc-api-sf-dev.us-e2.cloudhub.io}
- aria.basepath = {Aria base path, e.g., /api}
- aria.offerEndpoint = {Aria product offering endpoint, e.g., /productOffering}
- aria.specificationEndpoint = {Aria product specification endpoint, e.g., /productSpecification}
- externalSystems = {Comma-separated list of external systems, e.g., aria}

Secure Properties:
- secure.key = {Encryption key for secure properties, default: MuleS0ft!Secur!tyKey}
- secure::tls.keyStoreSecret = {TLS keystore password}
- secure::tls.keySecret = {TLS key password}

OAuth2 Client Credentials Authentication

The application uses OAuth2 client_credentials grant type for Salesforce authentication. Ensure you have:
1. Created a Connected App in Salesforce
2. Enabled OAuth settings with the appropriate scopes
3. Obtained the Consumer Key (Client ID) and Consumer Secret (Client Secret)
4. Configured the token URL based on your Salesforce instance (Production, Sandbox, or Custom Domain)

The OAuth tokens are automatically cached in an Object Store to minimize authentication requests.